Using a signal route dependent on a node speed change prediction

ABSTRACT

A device, method, computer program product, and network subsystem are described for receiving wireless data via a node-speed-change-prediction-dependent signal route and relaying at least a portion of the wireless data.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to, claims the earliest availableeffective filing date(s) from (e.g., claims earliest available prioritydates for other than provisional patent applications; claims benefitsunder 35 USC §119(e) for provisional patent applications), andincorporates by reference in its entirety all subject matter of thefollowing listed application(s) (the “Related Applications”) to theextent such subject matter is not inconsistent herewith; the presentapplication also claims the earliest available effective filing date(s)from, and also incorporates by reference in its entirety all subjectmatter of any and all parent, grandparent, great-grandparent, etc.applications of the Related Application(s) to the extent such subjectmatter is not inconsistent herewith. The United States Patent Office(USPTO) has published a notice to the effect that the USPTO's computerprograms require that patent applicants reference both a serial numberand indicate whether an application is a continuation or continuation inpart. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOElectronic Official Gazette, Mar. 18, 2003. The present applicant entityhas provided below a specific reference to the application(s) from whichpriority is being claimed as recited by statute. Applicant entityunderstands that the statute is unambiguous in its specific referencelanguage and does not require either a serial number or anycharacterization such as “continuation” or “continuation-in-part.”Notwithstanding the foregoing, applicant entity understands that theUSPTO's computer programs have certain data entry requirements, andhence applicant entity is designating the present application as acontinuation in part of its parent applications, but expressly pointsout that such designations are not to be construed in any way as anytype of commentary and/or admission as to whether or not the presentapplication contains any new matter in addition to the matter of itsparent application(s).

Related Applications:

1. For purposes of the USPTO extra-statutory requirements, the presentApplication constitutes a continuation-in-part of U.S. patentapplication entitled SIGNAL ROUTING DEPENDENT ON A NODE SPEED CHANGEPREDICTION, naming Alexander J. Cohen; Edward K. Y. Jung; Robert W.Lord; John D. Rinaldo, Jr.; and Clarence T. Tegreene as inventors, U.S.application Ser. No.: 11/252,258, filed Oct. 17, 2005 filedcontemporaneously herewith.

2. For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in part of U.S. patentapplication entitled SIGNAL ROUTING DEPENDENT ON A LOADING INDICATOR OFA MOBILE NODE, naming Alexander J. Cohen; Edward K. Y. Jung; Robert W.Lord; John D. Rinaldo, Jr.; and Clarence T. Tegreene as inventors, U.S.application Ser. No.: 11/252/206, filed Oct. 17, 2005, filedcontemporaneously herewith.

SUMMARY

An embodiment provides a communication method. In one implementation,the method includes but is not limited to receiving wireless data via anode-speed-change-prediction-dependent signal route and relaying atleast a portion of the wireless data. In addition to the foregoing,other communication method aspects are described in the claims,drawings, and text forming a part of the present disclosure.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting the hereinreferenced method aspects; the circuitry and/or programming can bevirtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a network subsystem. In one implementation, thesubsystem includes but is not limited to a module for receiving wirelessdata via a node-speed-change-prediction-dependent signal route andcircuitry for relaying at least a portion of the wireless data. Inaddition to the foregoing, other network subsystem aspects are describedin the claims, drawings, and text forming a part of the presentdisclosure.

In addition to the foregoing, various other embodiments are set forthand described in the text (e.g., claims and/or detailed description)and/or drawings of the present description.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processesdescribed herein, as defined by the claims, will become apparent in thedetailed description set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows a schematic diagram of a network in which a subsystem is anembodiment.

FIG. 2 shows a network in a schematic form including a network subsystemthat can interact with or become part of a signal route from a sourcenode to a mobile node.

FIG. 3 shows an operational flow having operations that facilitate adesirable form of data transfer.

FIG. 4 shows other flow embodiments that have operations that facilitateanother desirable form of data transfer.

FIG. 5 shows other flow embodiments that have operations that facilitateanother desirable form of data transfer.

FIG. 6 shows a device such as a computer program product including asignal bearing medium such as a conduit, a memory element, or a displaymedium.

FIG. 7 shows a network subsystem embodiment in schematic form.

FIG. 8 shows another network subsystem embodiment that includes avehicle.

FIG. 9 shows a look-up table that can be used for determining asuitability value at least partly based on each of several operands.

FIG. 10 shows a map plotting each of several nodes described in relationto the table of FIG. 9.

FIG. 11 shows another network subsystem in schematic form.

FIG. 12 shows another system embodiment.

FIG. 13 shows several variants of the flow of FIG. 3.

FIG. 14 shows several other variants and optional features of the flowof FIG. 3 or of its variants shown in FIG. 13.

FIG. 15 shows several further variants and optional features of the flowof FIG. 3 or its variants.

FIG. 16 shows several further variants and optional features of the flowof FIG. 3 or its variants.

FIG. 17 shows several further variants and optional features of the flowof FIG. 3 or its variants.

FIG. 18 shows several further variants and optional features of the flowof FIG. 3 or its variants.

FIG. 19 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 20 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 21 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 22 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 23 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 24 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 25 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 26 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 27 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 28 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 29 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 30 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 31 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 32 shows further optional features defining variants of the flow ofFIG. 3 or its variants.

FIG. 33 shows several optional features each defining variants of theflows of FIG. 5.

FIG. 34 shows several optional features each defining variants of theflows of FIG. 5 or their variants of FIG. 33.

FIG. 35 shows several optional features each defining variants of theflows of FIG. 5 or their variants.

FIG. 36 shows several other optional features each defining variants ofthe flows of FIG. 5 or their variants.

FIG. 37 shows several other optional features each defining variants ofthe flows of FIG. 5 or their variants.

FIG. 38 shows several other optional features each defining variants ofthe flows of FIG. 5 or their variants.

FIG. 39 shows several other optional features each defining variants ofthe flows of FIG. 5 or their variants.

FIG. 40 shows several other optional features each defining variants ofthe flows of FIG. 5 or their variants.

FIG. 41 shows several other optional features each defining variants ofthe flows of FIG. 5 or their variants.

FIG. 42 shows several optional features each defining variants of theflows of FIG. 4.

FIG. 43 shows several optional features each defining variants of theflows of FIG. 4 or their variants of FIG. 42.

FIG. 44 shows several other optional features each defining variants ofthe flows of FIG. 4 or their variants.

The use of the same symbols in different drawings typically indicatessimilar or identical items.

DETAILED DESCRIPTION

FIG. 1 shows a schematic diagram of a network 100 having a subsystem 110with data routed via route 180 between node 140 and node 190, which arephysically remote from one another (separated by about 10 meters ormore, e.g.). Route 180 can include channel 150 or one or more parallelchannels 160. Channel 150 can be arranged in series with an upstreamwireless link 145 and a downstream wireless link 185. Channel 150includes node 154 through which channel 150 passes. Channel 150 may alsoinclude one or more in-channel links 155 and one or more additionalchannel nodes 156. Subsystem 110 optionally includes channel controller170 that can include circuitry of node 140, node 190, or the in-channelnode(s) 154, 156 as shown. Channel controller 170 can also be composedpartially or entirely outside of all intermediate nodes available forrouting the data

As described below, route 180 can also include a linkage 135 to one ormore source nodes 133 further upstream, optionally outside network 100.Route 180 can likewise include a linkage 195 to one or more destinationnodes 197, optionally outside network 100. Alternatively oradditionally, node 140 can communicate with node 190 by one or moreother routes 182 such as by channel 162.

Referring now to FIG. 2, there is shown a network 200 in a schematicform, including a network subsystem 220 that can interact with or becomepart of a signal route 210 from source node 212 to a mobile node 240.Source node 212 is optionally configured to receive data fromspeedometer 248 of mobile node 240, and can also include a modeler 218that can receive location data 247 from mobile node 240. Networksubsystem 220 includes a module 225 configured to receive data directlyor indirectly from source node 212 and to provide information tocircuitry 227. Circuitry 227 can optionally apply one or more criteria228 to the data in determining how, when, or where to transmit the data,as explained below.

Referring now to FIG. 3, there is shown an operational flow 300 havingoperations that facilitate a desirable form of data transfer. After astart operation, flow 300 moves to a determining operation 330 ofdetermining a node-speed-change-prediction-dependent signal route and toa routing operation 350 of routing wireless data along the determinednode-speed-change-prediction-dependent signal route. A “prediction” orpredictive value may include a function of time, a quantity, anidentifier, a single Boolean value, a prose description, a probabilisticmodel of future or other uncertain attributes or behaviors, or someother characterization of a prediction. As described below, operation330 and operation 350 can be performed by source node 212 or by networksubsystem 220 of FIG. 2. After completing routing operation 350, flow300 moves to an end operation. More generally, flows described hereinneed not occur in the prescribed order, and in some cases may warrantsome interspersion or other overlap.

Referring now to FIG. 4, there are shown alternative operational flows400 having operations that facilitate another desirable form of datatransfer. After a start operation, flows 400 move to an obtainingoperation 430 of obtaining a node identifier dependent on at least aposition index and a loading indicator of a mobile node and to a routingoperation 450 of routing data through the mobile node responsive to thenode identifier. As described below, operation 430 and operation 450 canbe performed by source node 212 or by network subsystem 220 of FIG. 2.They can likewise be performed by controller 170 or by any of severalnodes of FIG. 1. Node 190 can perform a variant of flow 400, forexample, by including in the routing operation 450 an operation 455 ofperforming one or more error correction operations on at least a portionof the data.

Referring now to FIG. 5, there are shown alternative operational flows500 having operations that facilitate another desirable form of datatransfer. After a start operation, flow 500 moves to a receivingoperation 530 of receiving wireless data via anode-speed-change-prediction-dependent signal route and to a relayingoperation 550 of relaying at least a portion of the wireless data. Asdescribed below, operation 530 and operation 550 can be performed bysource node 212 or by network subsystem 220 of FIG. 2, for example. Theycan likewise be performed by controller 170, by any of several nodes ofFIG. 1, or by a combination of more than one of these. Controller 170can perform a variant of flow 500 by including in relaying operation 550an operation 555 of including at least some photographic image data inthe wireless data.

Referring now to FIG. 6, there is shown a device 600 such as a computerprogram product including a signal bearing medium 650 such as a conduit,a memory/storage element, a display medium, or a combination of morethan one type of medium. With reference to FIG. 3, medium 653 can bearone or more instructions for performing determining operation 330 andone or more instructions for performing routing operation 350.Alternatively or additionally, with reference to FIG. 4, medium 654 canbear one or more instructions for performing obtaining operation 430 andone or more instructions for performing routing operation 450.Alternatively or additionally, with reference to FIG. 5, medium 656 canbear at least one or more instructions for performing receivingoperation 530 and one or more instructions for performing relayingoperation 550.

Referring now to FIG. 7, there is shown a network subsystem 700 inschematic form. Subsystem 700 includes a module 750 for receivingwireless data from a node-speed-change-prediction-dependent signal routeand circuitry 770 for relaying at least a portion of the wireless data.(Although these are distinct in schematic form, circuitry 770 canoverlap or even occupy module 750 physically.)

Optionally, module 750 can include an amplifier 751 for amplifying atleast the portion of the wireless data. Alternatively or additionally,module 750 can include a signal-bearing conduit 752 for receiving atleast the portion of the wireless data. Module 750 can likewise includean antenna 754 operable to receive the wireless data and optionally adriver 755 configured to adapt a directionality of the antenna. Module750 can also include a user interface 757 operable to display at leastthe portion of the wireless data. Alternatively or additionally, module750 can include a controller 758 operable to transmit at least theportion of the received wireless data to the circuitry and/or acontroller 759 having a memory operable to hold at least some of theportion of the received wireless data.

Circuitry 770 optionally includes a controller 778 having a memory 779operable to contain one or more instructions that when executed causethe controller 778 to process at least some of the wireless data. Forexample, the instruction(s) can include machine code for transferring aportion of the wireless data to or from a register. Circuitry 770 canlikewise include one or more of circuitry 771 for implementing a look-uptable having a speed as an operand, circuitry 772 for implementing atime-dependent traffic model, circuitry 774 for implementing alocation-dependent speed model, or circuitry 775 for implementing avehicle-dependent speed model. In one embodiment, the circuitry 772 forimplementing a time-dependent traffic model includes circuitry 773 forimplementing a look-up table having a time as an operand. Moregenerally, circuitry 770 can include logic 776, such as logic 777 forimplementing a look-up table. For example, logic 777 can include logicfor accessing a storage element containing part or all of the table.

Referring now to FIG. 8, there is shown a network subsystem 800embodiment. Any or all of the nodes of FIG. 1 can be embodied as vehicle810 of network subsystem 800, for example. Vehicle 810 includes acommunication system 830, a drive mechanism 860 operable to startvehicle 810 moving, and a common power source 820. Power source 820 canbe operable to provide power selectively to drive mechanism 860(optionally via drive shaft 865) or to the circuitry such ascommunication system 830. For example, power source 820 can include acombustion engine 824 operable to provide power to drive shaft 865 andto an electrical supply 822 of power source 820. Electrical supply 822can selectively provide power to controller 834 or to antenna system839, an antenna operably coupled to a transceiver. Controller 834 caninclude a processor 837 operably coupled to an interface 836 and amemory 838. Antenna system 839 can be coupled to controller 834, such asby a conduit 833 coupled to processor 837. Interface 836 can beaccessible to a user 885 in a passenger compartment 880 of vehicle 810.User 885 can be a driver, pilot, or other passenger. Memory 838 can beconfigured as the signal-bearing medium 650 in any of the configurationsof FIG. 6. Processor 837 can thus perform one or more of flows 300, 400or 500 as described herein.

The network subsystem 800 can include a module (antenna system 839,e.g.) for receiving wireless data from anode-speed-change-prediction-dependent signal route (channel 870, e.g.)and circuitry (controller 834, e.g.) for relaying at least a portion ofthe wireless data.

In an embodiment in which power source 820 is operable to provide powerselectively to the drive mechanism 860 (to drive shaft 865, e.g.) or tothe circuitry of controller 834, network subsystem 800 can furtherinclude a combustion engine 824 operatively coupled (via electricalsupply 822, e.g.) to provide power to the circuitry. Also GPS 840 orcompass 850 can be coupled (via a short range wireless connection toantenna system 839, e.g.) to provide a signal to the processor 837.

Turning now to FIG. 9, there is shown a look-up table 900 that can beused for determining a suitability value 960 at least partly based oneach of several operands including operand 941 through operand 949. Inthe network subsystem 700 of FIG. 7, for example, table 900 can beimplemented in logic 777. Alternatively, in the vehicle 810 of FIG. 8,table 900 can be stored in memory 838. Optionally at least part of table900 can be in a random-access storage device such as a disk drive.

Operand 941 is (a fractional-degree portion of a latitude coordinate.Operand 942 is (a whole-degree portion of) a longitude coordinate.Operand 943 is (a fractional-degree portion of) a longitude coordinatecomplementing operand 941. Operand 944 is an altitude expressed inmeters relative to ground or sea level, providing for altitude-dependentsuitability indicators of aircraft that are passenger vehicles. Operand945 is a speed of a node, relative or absolute, expressed in meters persecond. Operand 944 and operand 945 are marked with asterisks toindicate an exponential scale in which each binary number is taken to bea power of 2. For the operand vector of row 973, for example, theindicated altitude is approximately 2 to the power of 0 (=1) meter aboveground and the indicated speed is approximately 2 to the power of 6=64meters per second.

Operand 946 is a node heading in which (magnetic) North=0000 and theother compass points increase clockwise to 1111 (NNW). Operand 946 isignored, however, for rows in which operand 945=0000. (In effect, speedsof 1 meter per second or less are treated as being stationary, in thismodel.)

Operand 949 is an information format indicator, which can be encoded toindicate video, audio, proprietary, encoded, or any of the otherformat-indicative descriptors used in this document as a matter ofdesign choice in light of present teachings. Additional operands 955 canalso be used in determining suitability value 960.

Referring now to FIG. 10 in light of FIG. 9, FIG. 10 shows a map 1000plotting latitude 1041 against longitude 1042. A location of each ofnode 1060 through node 1073 is also plotted on map 1000, some or all ofwhich are suitable for relaying information. Node 1061 is shown at39.070 degrees North, 104.287 degrees West, for example, in thisdetailed illustration. Referring again to FIG. 9, row 961 corresponds tooperands that describe node 1061. Node 1061 is therefore essentiallystationary, as indicated by the 0000 in the column of operands 945.

Row 962 is identical to row 961 except for the data format (at column949, e.g.) and the suitability value (at the column of values 960). Row961 has a suitability value of 11001, a binary number that indicates ahigh suitability. Row 962 indicates an even higher suitability, though,illustrating that the model implemented in table 900 has aformat-dependent suitability indicator at the column of values 960.

Row 963 of FIG. 9 corresponds to operands that describe node 1063 ofFIG. 10. Row 963 and row 964 illustrate that the model implemented intable 900 has a speed-dependent suitability indicator (in the column ofvalues 960), having operand values that are identical except for speed(in the column of operands 945). Therefore the suitability indicator ofnode 1063 would decrease (from 11111 to 10100, according to table 900)if the speed of node 1063 were about 8 meters per second rather thanbeing at most about 1 meter per second.

Row 965 of FIG. 9 corresponds to operands that describe node 1065 ofFIG. 10. Operand 948 is a binary load indicator such that 000 indicatesno loading and 111 indicates saturation, in terms of a fractional usageof a critical resource such as a maximum data transfer rate and/or areduction of available space in a memory such as memory 838 in theembodiment of FIG. 8 described above. Row 965 and row 966 illustratethat the model implemented in table 900 has a load-dependent suitabilityindicator, having operands that are identical except for load (in thecolumn of operands 948). Therefore the suitability indicator of node1065 would increase (from 01010 to 11010, according to table 900) if theload indicator of node 1065 were 010 rather than being 101.

Row 968 of FIG. 9 corresponds to operands that describe node 1068 ofFIG. 10. Row 967 and row 968 illustrate that the model implemented intable 900 has a heading-dependent suitability indicator (in the columnof values 960), having operand values that are identical except forheading (in the column of operands 946). Therefore the suitabilityindicator of node 1068 would increase (from 10110 to 11111, according totable 900) if the heading of node 1068 were eastward (dir=0100) ratherthan westward (dir=1100).

Rows 969 & 970 of FIG. 9 correspond respectively to operands thatdescribe nodes 1069 & 1070 of FIG. 10. Rows 969 & 970 illustrate thatthe model implemented in table 900 has a position-index-dependentsuitability indicator (in the column of values 960), having operandvalues that are identical except for latitude (in the column of operands941). Node 1069 and node 1070 are both traveling north at about 32 m/s.The suitability indicator of node 1069 is higher than that of node 1070,according to table 900, just because it is not as far north.

Row 973 of FIG. 9 corresponds to operands that describe node 1073 ofFIG. 10. Operand 947 is a node class indicator corresponding toattributes of a given node that affect its ability to provide service.Operand 947 can indicate some combination of a nominal antenna range, anominal transmitter power, a nominal bandwidth, a nominal gain-bandwidthproduct, a nominal data rate, a wireless protocol, a service provider,or a service level, for example. In one implementation, operand 947=0011uniquely indicates a combination of node attributes that include anominal operating frequency of 900 MHz and/or 1,800 MHz and anunlimited-duration service. Other values of operand 947 shown indicateno such nominal operating frequency and/or limited-duration service, forexample, when table 900 is used in any of the above-described flows.

Row 972 and row 973 illustrate that the model implemented in table 900has a load-dependent suitability indicator, having operand values thatare identical except for node class (in the column of operands 947).Therefore the suitability indicator of node 1073 would decrease (from01001 to 00110, according to table 900) if the class of node 1073 were0110 rather than being 0100.

Additional rows 975 are too numerous to be shown effectively on paper.Table 900 is large, in fact, and in some contexts it would be convenientto use a simpler model. One way to do this would be to implement a tablein a stationary router for a given area of land, and to use a localmodel that assumes a local value of one or more position indices withina zone (by omitting column of operands 942, for example). Part of themodel can be executed before looking up the suitability value,alternatively or additionally, such as by using a route that includesone or more predicted speeds to predict a location at a given futurepoint in time. By using a prediction that has been computed in a priorcomputational operation, for example, the heading or speed operands canbe omitted from the look-up operation.

Referring now to FIG. 11, there is shown another network subsystem 1100including a module 1150 and circuitry 1170 in schematic form. Module1150 can be configured for receiving wireless data from anode-speed-change-prediction-dependent signal route and includecircuitry 1170 configured for relaying at least a portion of thewireless data. Subsystem 1100 can further include a power source such asa fuel cell 1121 or photovoltaic cell 1122 operatively coupled toprovide power to the components of circuitry 1170 or module 1150. Module1150 can include an antenna 1152, a processor 1153, or a memory 1159.

Alternatively or additionally, module 1150 can be configured forobtaining a node identifier dependent on at least a position index and aloading indicator of a mobile node, and circuitry 1170 can be configuredfor routing data through the mobile node responsive to the nodeidentifier. Circuitry 1170 can include a transmitter 1173 or transceiver1174 operable to communicate with the mobile node. For example, thetransceiver can receive the position index and the loading indicator,which processor 1153 can use to generate the node identifier ofwhichever of the available nodes (of mobile node 1181 and mobile node1182, e.g.) is most suitable for relaying a signal to a stationary node(tower 1183, e.g.). Circuitry 1170 can also include a controller 1171,optionally one with access to a medium 1172 configured as medium 1240 ofFIG. 12. Alternatively, medium 1172 can be a transmission medium (suchas a conduit) or a medium of communication (such as a display, e.g.).

Referring now to FIG. 12, there is shown a system 1200 (which can benetwork subsystem 1100 or a computer program product 1220, e.g.) thatincludes at least a signal-bearing medium 1240. Signal bearing medium1240 can include one or more of a computer-readable medium 1245, arecordable medium 1246, a disk 1247, one or more determininginstruction(s) 1250, or one or more routing instruction(s) 1260. Thedetermining instruction(s) 1250 can be one or more instructions fordetermining a node-speed-change-prediction-dependent signal route. Thisinstruction set can include one or more of instruction(s) 1251,instruction(s) 1253, instruction(s) 1255, instruction(s) 1257, orinstruction(s) 1258. Instruction(s) 1251 refers to one or moreinstructions for determining the node-speed-change-prediction-dependentsignal route at least partly based on one or more measured speeds.Instruction(s) 1253 refers to one or more instructions for determiningthe node-speed-change-prediction-dependent signal route at least partlybased on a traffic report. Instruction(s) 1255 refers to one or moreinstructions for determining the node-speed-change-prediction-dependentsignal route at least partly based on a schedule. Instruction(s) 1257refers to one or more instructions for determining thenode-speed-change-prediction-dependent signal route at least partlybased on a vehicular travel prediction. Instruction(s) 1258 refers toone or more instructions for determining thenode-speed-change-prediction-dependent signal route at least partlybased on one or more speed limits. One or more routing instruction(s)1260 refers to one or more instruction(s) for routing wireless dataalong the determined node-speed-change-prediction-dependent signalroute.

Referring now to FIG. 13, there are shown several variants of flow 300of FIG. 3. For example, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 1331, operation 1333, operation 1335, or operation1337. Operation 1331 includes identifying a first node by routeinformation received by a second node. Operation 1333 includes modifyingthe node-speed-change-prediction-dependent signal route at least partlybased on state information from outside thenode-speed-change-prediction-dependent signal route. (An item “outside”a route or set is not limited to permanently excluded items, but alsorefers to candidates for inclusion within the route or set., e.g.) Aflow is also shown including operation 1335 of receiving stateinformation about a node and operation 1337 of excluding the node fromthe node-speed-change-prediction-dependent signal route at least partlybased on the state information.

Any of these features can optionally be used in combination with any ofthe variants of operation 350, routing wireless data along thedetermined node-speed-change-prediction-dependent signal route.Operation 350 can include an operation 1355 of streaming at least aportion of the wireless data. The data streaming is not limited todirecting unidirectional data flow in a single channel, but can includeany technique for handling data at one or more stages in a steady andcontinuous stream, typically facilitated by buffering and/ormultiplexing at least some of the data. Alternatively or additionally,operation 350 can include an operation 1358 of including at least a datapriority indication in the wireless data. A high priority may indicatethat the data is of a time-sensitive nature, that the data is likely tobe relatively small, or that the sender, owner or receiver has a highstatus relative to that of some other messages.

Referring now to FIG. 14, there are shown several other variants andoptional features of flow 300 of FIGS. 3 & 13. For example, theoperation 330 of determining a node-speed-change-prediction-dependentsignal route can include one or more of operation 1431, operation 1435,operation 1437, or operation 1439. Operation 1431 includes receivinginformation from outside the node-speed-change-prediction-dependentsignal route. In performing flow 300, node 140 can receive stateinformation from node 154 in FIG. 1, for example, indicating that node154 is expected to be stopped and unavailable for service imminently. Ifnode 140 then receives a transmission along a signal route 180 that onlyincludes a linkage 135 from source node 133 to intermediate node 140,for example, node 140 can then respond by appending channel 160 tosignal route 180 responsive to the node speed change prediction fromnode 154.

Alternatively or additionally, node 140 can receive from outside thenode-speed-change-prediction-dependent signal route a prediction of atleast one of a node speed or a node speed change (by operation 1435,e.g.) or of a node heading or a node heading change (by operation 1437,e.g.). Node 140 can use one or more of these items of information topredict a node speed change from which to determine at least part ofsignal route 180.

In lieu of any of receiving operations 1431, 1435, and 1437, node 140can instead receive a zone identifier from outside thenode-speed-change-prediction-dependent signal route (such as route 180,by operation 1439, e.g.). For example, node 140 can receive the zoneidentifier as an indication of where node 154 will be at a given moment,based on a speed change prediction. Node 140 can use thisnode-speed-change-prediction-dependent zone identifier in determining toappend channel 150 in lieu of channel 160 (by operation 330, e.g.).

In combination with any of the above-described variants of operation330, the routing operation 350 can also comprise operation 1451 oroperation 1453. Operation 1451 comprises including at least a dataownership indication in the wireless data. This is not limited to acopyright notice but can also be an anonymous indication that the datais proprietary. Operation 1453 comprises including at least adestination indication in the wireless data. For example, the indicationcan be a geographic zone, a destination network, or a particular node orentity.

Referring now to FIG. 15, there are shown several further variants andoptional features of flow 300 of FIGS. 3, 13, and 14. For example, theoperation 330 of determining a node-speed-change-prediction-dependentsignal route can include one or more of operation 1531, operation 1535,operation 1537, or operation 1539. Operation 1531 includes receivingfrom outside the node-speed-change-prediction-dependent signal route atleast one of a latitude prediction, an altitude prediction, a zoneidentifier prediction, a node deceleration prediction, a nodeacceleration prediction, a node orientation prediction, or a predictednode orientation change. For example, the received information caninclude a description of a node that is a candidate for addition to thenode-speed-change-prediction-dependent signal route. Similarly, thedetermining operation 330 can include receiving a node speed prediction(by operation 1535, e.g.), receiving a node speed change prediction (byoperation 1537, e.g.), or receiving a node heading prediction (byoperation 1539, e.g.).

Alternatively or in combination with any of the above-described variantsof operation 330 or operation 350, the routing operation 350 can furthercomprise including at least an estimate of a destination's positionindex (by operation 1553, e.g.) or including at least an estimate of anarrival time (by operation 1556, e.g.) in the wireless data. Forexample, the position index can be an altitude, a set of coordinates, oran offset distance from some reference point. The arrival time is notlimited to an arrival time of a signal but can alternatively describe aplanned or otherwise approximate arrival of one or more nodes or otherphysical objects.

Referring now to FIG. 16, there are shown several further variants andoptional features of flow 300 of FIG. 3, 13, 14, or 15. For example, theoperation 330 of determining a node-speed-change-prediction-dependentsignal route can include one or more of operation 1631, operation 1634,operation 1637, or operation 1639. The operation 350 can similarlyinclude one or more of operation 1655 or operation 1658.

For example, referring again to FIG. 1, node 154 can receive a nodeheading change prediction (by operation 1631, e.g.) or receive aprediction of a zone identifier (by operation 1634, e.g.) that node 154uses for determining a node-speed-change-prediction-dependent signalroute (by operation 330, e.g.). For example, node 154 can be astationary node that receives one or more predictions bearing upon theavailability and suitability of a mobile node, which can be node 156.Node 154 can use the one or more predictions to determine a route, whichcan be route 180 amended to include channel 150. Node 154 can respond byrouting wireless data along the determinednode-speed-change-prediction-dependent signal route (by operation 350,e.g.), and optionally by encrypting at least part of the wireless data(by operation 1655, e.g.) before completing the routing operation 350.

In another example, node 156 can receive a prediction of an antennaposition (by operation 1639, e.g.) or another node component position(by operation 1637, e.g.) in performing the determining operation 330.For example, node 156 can receive a prediction that a component of node190 will be in a given position enabling transmission through node 156at a given time. Node 156 can use this prediction in responding to arouting request broadcast indicating that node 140 has a message fornode 197. Node 156 can determine anode-speed-change-prediction-dependent signal route (by operation 330,e.g.) at least to node 190 and route wireless data along the route (byoperation 350, e.g.) by transmitting the route to node 140.

In another example in which node 140 is a source node, node 140 canperform one of the above-described variants of flow 300 in which therouting operation 350 comprises including at least audio data in thewireless data (by operation 1658, e.g.). Audio data included byoperation 1658 is not limited to telephonic data, but can also includemusic, speech, or other recordings or artificial sounds. The audio datais optionally encrypted by node 140 also, such as by operation 1655.

Referring now to FIG. 17, there are shown several further variants andoptional features of flow 300 of FIG. 3, 13, 14, 15, or 16. For example,the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 1733, operation 1734, operation 1737, or operation1738. The operation 350 can similarly include one or more of operation1752 or operation 1753. Operation 1733 includes receiving a predictionof at least one of a longitude, an altitude, a zone identifier, alocation, a position index, a node deceleration, a node acceleration, anode orientation, a node orientation change, or a node heading change.For example, source node 212 of FIG. 2 can receive any or all of thesein describing mobile node 240. Node 212 can use this information in thedetermining operation 330 and respond by performing the routingoperation 350. Optionally the routing operation 350 can compriseincluding at least user-specified data in the wireless data (byoperation 1752, e.g.). The routing operation 350 can also compriserouting one or more information describing one remote node (node 240,e.g.) to another remote node (one that includes module 225, e.g.).

In one example, network subsystem 220 receives a node description (byoperation 1737, e.g.) in performing the determining operation 330. Forexample, network subsystem 220 can receive an indication of a node class(by operation 1734, e.g.) or can receive node state information (byoperation 1738, e.g.) from source node 212. Network subsystem 220 cancomplete the determining operation 330 by deciding to route data along asignal route to mobile node 240. Optionally network subsystem 220reserves at least a portion of the determinednode-speed-change-prediction-dependent signal route (by operation 350and including operation 1753, e.g.).

Referring now to FIG. 18, there are shown several further variants andoptional features of flow 300 of FIG. 3, 13, 14, 15, 16, or 17. Forexample, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 1831, operation 1832, operation 1835, or operation1836. The operation 350 can similarly include one or more of operation1857 or operation 1858. For example, module 1150 of FIG. 11 can performany of these variants of the determining operation 330, includingreceiving node load information 1831, receiving a definition of thenode-speed-change-prediction-dependent signal route 1835, or receiving asuitability indicator 1836. Alternatively or additionally, module 1150can receive at least one of a definition of thenode-speed-change-prediction-dependent signal route, a suitabilityindicator, node state information, a node description, or node classinformation 1832.

Circuitry 1170 can route wireless data along the signal route determinedby module 1150, such as by a route through mobile node 1181 to tower1183. Circuitry 1170 can also perform operation 1857 by displaying atleast a portion of the wireless data within a mobile node (withinsubsystem 1100, which may be a vehicle, e.g., via medium 1172). Ifnetwork subsystem 1100 is not a vehicle, circuitry 1170 can stilldisplay at least a portion of the wireless data via an element of amobile node (by performing displaying operation 1858, e.g., via medium1172).

Referring now to FIG. 19, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, or 18. For example,the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 1931, operation 1935, operation 1937, or operation1939. For example, network subsystem 800 of FIG. 8 can perform many ofthese variants. Antenna system 839 can perform the operation 1931 ofreceiving a burden indicator, for example, optionally in combinationwith operation 1537 of receiving a node speed change prediction.Alternatively or additionally, antenna subsystem 839 can perform theoperation 1935 of receiving at least one of node state information, adefinition of the determined node-speed-change-prediction-dependentsignal route, a suitability indicator, a node description, or node classinformation.

Similarly, controller 834 can perform the operation 1937 of storinginformation about a node outside thenode-speed-change-prediction-dependent signal route and the operation1939 of determining the node-speed-change-prediction-dependent signalroute at least partly based on the information. Controller 834 canreceive and store node state information and other descriptions from orabout nearby nodes, for example, in memory 838. In response to a routerequest, processor 837 can then use or provide the stored informationfor the determining operation 1937.

Optionally, the routing operation 350 can include one or more ofoperation 1956 or operation 1959. Communication system 830 can routeother wireless data along another signal route parallel to thedetermined node-speed-change-prediction-dependent signal route (atoperation 1956, e.g.). For example, system 830 can determine two or moreparallel channels across which to spread received data, such as by codedivision or time division multiplexing. Alternatively or additionally,communication system 830 can await an acknowledgment signal beforesending a portion of the wireless data along the determinednode-speed-change-prediction-dependent signal routes (at operation 1959,e.g.).

Referring now to FIG. 20, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, or 19. Forexample, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 2031, operation 2035, operation 2036, operation 2038,or operation 2039. For example, node 140 of FIG. 1 can be configured asa device 600 that includes a signal bearing medium 650 containinginstructions 653. The one or more instructions for performingdetermining operation 330 can enable node 140 to request informationfrom outside the node-speed-change-prediction-dependent signal route (atoperation 2031, e.g.) in performing flow 300. Node 140 can poll allnodes within a direct-transmission zone of node 140 for a route table,for example, which includes information about a plurality of channelsnot yet on a given signal's defined route. These channels can includechannel 150, channel 160, and channel 162, for example. Node 140 can usethis information in determining route 180, such as by appending channel150 to whatever route through which node 140 receives the data.

Node 140 can also perform operation 2035 of obtaining at least one of anode speed prediction or a node speed change prediction, optionally byoperation 2036 of estimating a future speed of a node such as node 154.Node 140 can estimate at least one of a node heading or a node headingchange 2038 (of node 154, e.g.). Alternatively or additionally, node 140can perform operation 2039 of receiving a predictive zone identifierfrom outside the node-speed-change-prediction-dependent signal route.For example, node 140 can receive from node 156 a predictive or otherzone identifier describing a past or future location of node 156, anduse this information in determining thenode-speed-change-prediction-dependent signal route through channel 150.Optionally, the full signal route definition (i.e. all the way from asource node) can be included in a transmission sent to node 154 and node156.

Optionally, the same network subsystem that performs the determiningoperation 330 can perform one or both of operation 2055 or operation2056. Operation 2055 includes converting at least a portion of thewireless data into optical data. For example, in an embodiment in whichlinkage 195 includes a fiberoptic or other optical communication link,node 190 of subsystem 110 can perform the converting operation 2055.Node 190 can also perform flow 300, alternatively or additionally, byrouting at least a portion of the wireless data to a stationary node (tonode 197 by operation 2056, e.g.).

Referring now to FIG. 21, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, 19, or 20. Forexample, network subsystem 1100 of FIG. 11 can perform one or more ofoperation 2132, operation 2133 or operation 2135. Operation 2132includes receiving at least one of a latitude prediction, an altitudeprediction, a zone identifier prediction, a location prediction, aposition index prediction, a node deceleration prediction, a nodeacceleration prediction, a node orientation prediction, a nodeorientation change, a node heading prediction, or a node heading changeprediction. Operation 2133 includes generating a node speed changeprediction, optionally based on one or more items received in operation2132 or one or more of operations 1531-1539. (“Generating” or“predicting” a value is not limited to computing a value anew, but canalso include translating, updating or otherwise adjusting another value,for example, such as a prediction received at operation 1535 oroperation 1537, e.g.) Network subsystem 1100 can also predict a nodeheading (by operation 2135, e.g.).

Referring again to FIG. 11, circuitry 1170 can perform operation 350 byperforming operation 2155 or operation 2156. Circuitry 1170 can route atleast a portion of the wireless data through a stationary node (such astower 1183, by operation 2155). Alternatively or additionally, circuitry1170 can route at least a portion of the wireless data through apassenger vehicle (such as through node 1182, which can be a passengervehicle, by operation 2156).

Referring now to FIG. 22, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, 19, 20 or 21.For example, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of an operation 2231 of predicting a node heading change, anoperation 2232 of generating a prediction of a node speed, an operation2237 of generating a zone identifier prediction, or an operation 2238 ofreceiving a prediction of an absolute position of a node component. Oneor more of operation 2231, operation 2232, operation 2237, or operation2238 can be performed by system 1200 including signal-bearing medium1240. Predicting operation 2231 is not limited to predicting the changeby a route received from a vehicle navigation system, but can includeusing any statistical or other bases for prediction. Similarly, a“prediction” or predictive value may include a function of time, asingle Boolean value, a prose description, a probabilistic model offuture or other unknown behavior, or other characterization of aprediction.

System 1200 can perform operation 350 also, optionally by operation 2255or by operation 2258. At operation 2255, system 1200 can route at leasta portion of the wireless data through a motor-propelled vehicle. Atoperation 2258, system 1200 can route at least a portion of the wirelessdata through a stationary node and a mobile node, such as bytransmitting an identifier of one or both of the nodes prior to ahandshake operation for establishing a link to the identified node.Optionally, an identifier for the other of the nodes can later beincluded in a transmission through the link.

Referring now to FIG. 23, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, 19, 20, 21, or22. For example, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 2331, operation 2334, operation 2336, or operation2339. Node 1060 of FIG. 10 can perform flow 300, optionally includingoperation 2331 of predicting an antenna position. The antenna positionneed not relate to an antenna of node 1060, but can relate to some otherantenna having a motion pattern that node 1060 can predict, such as asteadily rotating antenna of a tower.

Node 1060 can also generate a prediction of at least one of an altitude,a zone identifier, a node deceleration, a node acceleration, a nodeorientation, or a node orientation change (by operation 2334, e.g.). Forexample, node 1060 can generate a prediction of a node orientation asdefined in the column of operands 946. Such a generated value canoptionally be used as an operand in a subsequent function call, orotherwise as a circuit input, alone or in concert with other operands.For example, node 1060 can also generate an indication of a node class(by operation 2336) or generate a node description (by operation 2339).The node class or other description can be used as a correspondingoperand in a table like table 900.

In performing the operation 350 of routing wireless data along thedetermined node-speed-change-prediction-dependent signal route, node1060 can perform operation 2355 of routing at least a portion of thewireless data responsive to a user input. A wireless link may alreadyexist from node 1060 to another node within a wireless transmissionrange of node 1060 (such as node 1065 or node 1069, e.g.) as node 1060tries to route a new message, for example, responsive to an earlier userinput at node 1060. If so, node 1060 can take advantage of the existinglink in routing at least a portion of the wireless data. The user inputis not limited to an earlier input, but can be requested of the user inperforming routing operation 2355.

Alternatively or additionally, node 1060 can perform operation 2356 ofmultiplexing at least a portion of the wireless data. For example, someor all of the data can be distributed across two or more parallelchannels or multiplexed with other data through a single wirelesschannel.

Referring now to FIG. 24, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22or 23. For example, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 2431, operation 2435, operation 2437, or operation2439. Operation 2431 includes generating node state information.Operation 2435 includes generating node load information. At operation2437, a node or other system generates at least one of a definition ofthe node-speed-change-prediction-dependent signal route, node stateinformation, a node description, or node class information. Operation2439 includes generating a definition of thenode-speed-change-prediction-dependent signal route. Module 750 ofnetwork subsystem 700 can perform one or more of operation 2431,operation 2435, operation 2437, or operation 2439, for example. Theresulting information need not be used for routing or computations, butcan alternatively or additionally be displayed via user interface 757 orstored by controller 759.

In performing the operation 350 of routing wireless data along thedetermined node-speed-change-prediction-dependent signal route, nodecircuitry 770 can perform one or more of updating state information inthe wireless data (by operation 2455) or transmitting state informationin the wireless data (by operation 2456).

Referring now to FIG. 25, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,23, or 24. For example, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 2531, operation 2532, or operation 2537. Operation2531 includes generating a suitability indicator, optionally bygenerating a burden indicator (by operation 2532). This illustrates howa suitability indicator can be expressed as a value that is inverselyrelated to an actual suitability of a node. For example, if D is avariable such that D=0.9 for an unsuitable system, and D=0.3 for amoderately suitable system, and D=0.1 for a highly suitable system, thenD can be a convenient burden indicator. Such values, generally ones thatare inversely related to suitability, can be combined for evaluating achannel more exactly, in certain embodiments. With reference to channel150 of FIG. 1, for example, operation 2532 can be performed by summingat least a burden indicator of node 154 with a burden indicator of node156.

Operation 2537 includes generating at least one of node stateinformation, a definition of the determinednode-speed-change-prediction-dependent signal route, a suitabilityindicator, a node description, or node class information. Operation 2537is optionally performed within a network subsystem that also performsoperation 2555 (indicating an error in at least a portion of thewireless data) or operation 2556 (indicating a position of anintermediate node to a next-downstream-node). For example, in performingflow 300, node 154 of FIG. 1 can perform operation 2537 by generating adefinition of the determined node-speed-change-prediction-dependentsignal route, one that includes channel 150. In performing the routingoperation 350, node 154 can indicate an error, for example bytransmitting a re-send request to node 140. Alternatively, node 154 canindicate the error to trigger an error correction routine within node154, or can forward the wireless data without any correction.Alternatively or additionally, node 154 can use link 155 to indicate itsposition (by one or more position indices) to next-downstream node 156.

Referring now to FIG. 26, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,23, 24, or 25. For example, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 2634, operation 2635, operation 2637, or operation2639. Any of these variants can be performed for example, alone or inconcert with any of the optional features or operations described abovewith reference to FIG. 11. Processor 1153 can retrieve the stateinformation about a node outside thenode-speed-change-prediction-dependent signal route, for example, Aftersuch retrieval or other preparation, processor 1153 can transmit stateinformation about a node outside thenode-speed-change-prediction-dependent signal route (by operation 2634,e.g.) to circuitry 1170. Circuitry 1170 can then determine thenode-speed-change-prediction-dependent signal route (through or aroundthe node, by operation 2635, e.g.) at least partly based on the stateinformation. Alternatively or additionally, circuitry 1170 performsoperation 2639 of transmitting a prediction of at least one of a nodespeed or a node speed change. For example, circuitry 1170 can determinethe signal route by operation 2635 and dependent on a prediction of anode speed change. Circuitry 1170 can store the prediction for a latertransmission to a network server to facilitate network data aggregation.

In another embodiment, network subsystem 1100 can serve merely as arouter. Subsystem 1100 can perform the determining operation 330 bydetermining a route from mobile node 1181 through node 1182 to tower1183, for example. The determining operation 330 includes an operation2637 of transmitting information from a node outside thenode-speed-change-prediction-dependent signal route. For example, theinformation can include protocol information for completing acommunication link from network subsystem 1100 to mobile node 1181.

In performing the operation 350 of routing wireless data along thedetermined node-speed-change-prediction-dependent signal route,circuitry 1170 can instruct node 1181 to transmit the wireless data tomobile node 1182. The routing operation 350 can also include one or moreof indicating operation 2655 or indicating operation 2656. In indicatingoperation 2655, for example, circuitry 1170 can indicate a position ofan intermediate node (node 1182, e.g.) to a next-upstream-node (node1181, e.g.). In indicating operation 2656, circuitry 1170 can indicate asuitability of an intermediate node (node 1182, e.g.). The indicationcan be stored (in medium 1171, e.g.), used as an operational criterion(such as for determining a portion of the signal route), displayed, ortransmitted to another node (such as tower 1183).

Referring now to FIG. 27, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,23, 24, 25 or 26. For example, the operation 330 of determining anode-speed-change-prediction-dependent signal route can include one ormore of operation 2731, operation 2735, operation 2737, or operation2739. Network subsystem 1100 can obtain and then transmit from outsidethe node-speed-change-prediction-dependent signal route at least one ofan altitude prediction, a zone identifier prediction, a nodedeceleration prediction, a node acceleration prediction, a nodeorientation prediction, or a node orientation change indication (atoperation 2737, e.g.). This information for transmission can describenode 1182, for example. Whether subsystem 1100 generates the predictionor obtains it in some other way, subsystem 1100 can perform thetransmitting operation 2731 before, during or after other portions ofthe determining operation 330. This can likewise apply to transmitting aprediction of at least one of a node heading or a node heading change(operation 2731), transmitting a zone identifier (operation 2735) ortransmitting a prediction of a node speed (operation 2739). Any of thesetransmitting operations 2731-2739 can optionally be performed by anetwork subsystem outside the node-speed-change-prediction-dependentsignal route.

In performing the operation 350 of routing wireless data along thedetermined node-speed-change-prediction-dependent signal route,circuitry 1170 can optionally perform routing operation 2751 orindicating operation 2755. Circuitry 1170 can perform routing operation2751 by routing the wireless data along anode-speed-change-prediction-independent portion of thenode-speed-change-prediction-dependent signal route. Circuitry 1170 canperform indicating operation 2755 by indicating a suitability score ofthe node-speed-change-prediction-dependent signal route. Alternativelyor additionally, circuitry 1170 can perform routing operation 1956 suchas by routing the other wireless data along a parallel route, such as bya direct transmission through a free space medium to tower 1183. For acase in which network subsystem 1100 stays strictly outside thenode-speed-change-prediction-dependent signal route, however, circuitry1170 does not “send” any of the wireless data routed along the signalroute, and subsystem 1100 is in that case inconsistent with awaitingoperation 1956.

Referring now to FIG. 28, there are further optional features definingvariants of flow 300 of FIG. 3, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,23, 24, 25, 26, or 27. For example, the operation 330 thereof caninclude one or more of operation 2831 of transmitting a prediction of anode speed change, operation 2835 of transmitting a prediction of a nodeheading, operation 2837 of transmitting a node heading changeprediction, or operation 2839 of transmitting an identifier of a zone.Any of these transmitting operations 2831-2839 can be performed by anyof the above-described nodes that receive or generate such a change,heading, prediction, identifier or related descriptive information. Forexample, referring again to FIG. 1, node 190 can receive and transmitsuch descriptive information through linkage 195 or via channel 162,optionally with a timestamp that describes the information. Such atimestamp can be used to evaluate the recency and reliability of theinformation, for example.

Node 140 can optionally perform one or more of operations 2831-2839 whenperforming flow 300. Alternatively or additionally, at operation 2856,node 140 can indicate a suitability score of a signal route other thanthe node-speed-change-prediction-dependent signal route. For example,node 140 can perform the determining operation 330 by comparing asuitability score of channel 150 with that of channel 160. Node 140 candetermine the node-speed-change-prediction-dependent signal route 180 asincluding whichever of the channels was apparently more suitable,omitting the other channel from signal route 180. Node 140 can performthe indicating operation 2856 of the routing operation 350 foraccumulating a history of suitability scores of selected andnon-selected channels, for example. Node 140 can also identify one ormore mobile nodes of the determinednode-speed-change-prediction-dependent signal route, by operation 2857.

Referring now to FIG. 29, there are more optional features relating toflow 300 and its multiple variants as describe above. For example, theoperation 330 thereof can include one or more of operation 2931,operation 2935, operation 2937, or operation 2939. These are each atransmitting operation that can be performed as a part of flow 300 bynetwork subsystem 220, for example. Module 225 can perform operation2931 of transmitting a prediction of a node component position. Module225 can further perform operation 2935 of transmitting a prediction ofan antenna position, such as a position of an antenna of subsystem 220.Module 225 can also perform operation 2937 of transmitting a predictionof at least one of a longitude, an altitude, a zone identifier, alocation, a position index, a node deceleration, or a node acceleration.Any, some, or all of these predictions can be either generated orreceived by module 225 before or during operation 2937. Alternatively oradditionally, module 225 can transmit an indication of a node class (byoperation 2939) after receiving or generating the indication.

Operation 2955 includes performing an operation (such as displayingoperation 1858 or multiplexing operation 2356, e.g.) while determining anode-speed-change-prediction-dependent signal route (by one of theabove-described variants of operation 330, e.g.). Subsystem 220 canperform operation 2955, for example, by using module 225 for thedetermining operation 330 while using circuitry 227 for performing theother operation. The “other” operation can include one or more of theabove-described “indicating” operations (operation 2556, operation 2655,operation 2656, operation 2755, or operation 2856, e.g.) or one or moreof the above-described variant “routing” operations (operation 1956,operation 2056, operation 2155, operation 2255, operation 2258, oroperation 2355, e.g.) of routing operation 350, for example.

Referring now to FIG. 30, there are further optional features relatingto flow 300 and its multiple variant flows as describe above. Forexample, the operation 330 can include one or more of operation 3031 oftransmitting a node description, operation 3035 of transmitting nodestate information, or operation 3037 of transmitting node loadinformation. Part or all of channel 162 can perform flow 300 with one ormore of these operations, such as by transmitting the information orother description from or about node 140 or node 190. Alternatively oradditionally, part or all of channel 162 can transmit at least one of adefinition of the node-speed-change-prediction-dependent signal route, asuitability indicator, node state information, a node description, ornode class information, at operation 3039. One or more of theseoptionally describe a portion of channel 162. Channel 162 can optionallybegin the routing wireless data along the determinednode-speed-change-prediction-dependent signal route after finishing thedetermining a node-speed-change-prediction-dependent signal route, byoperation 3056.

Referring now to FIG. 31, there are further optional features relatingto flow 300 and its multiple variant flows as describe above. Forexample, the operation 330 can include one or more of operation 3131,operation 3135, operation 3137, operation 3138, or operation 3139.Referring again to FIG. 1, for example, node 190 can perform theoperation 3131 of transmitting a definition of thenode-speed-change-prediction-dependent signal route, the operation 3135of transmitting a suitability indicator, or the operation 3137 oftransmitting a burden indicator. Any of these operations can causeinformation to be transmitted upstream via channel 162 or downstream vialinkage 195, for example.

Some variants of flow 300 can be performed by controller 170, includingmany that incorporate one or more of executing operation 3138, receivingoperation 3139, or generating operation 3155. Executing operation 3138can be performed by executing one or more instructions for measuring aspeed of a node of the node-speed-change-prediction-dependent signalroute. For example, controller 170 can be configured as a device 600,including signal bearing medium 650 containing “one or more instructionsfor performing determining operation 330” of the instructions 653. Theinstructions 653 can further include the “one or more instructions formeasuring a speed” for execution at operation 3138. Receiving operation3139 includes receiving at a first node (such as node 140, e.g.) routeinformation identifying a second node (such as a downstream node 154 oran upstream node 133, e.g.). Generating operation 3155 (of routingoperation 350) includes generating at a first node (such as node 140,e.g.) route information identifying a second node (such as a node listincluding node 154 and node 156).

Referring now to FIG. 32, there are further optional features relatingto flow 300 and its multiple variant flows as describe above. Forexample, the operation 330 can include one or more of operation 3233,operation 3234, operation 3236, or operation 3239. Likewise the routingoperation 350 can include a transmitting operation 3256. Any of theseoptional features can optionally be performed by network subsystem 110performing flow 300. Module 1150 optionally transmits at least one ofnode state information, a definition of the determinednode-speed-change-prediction-dependent signal route, a suitabilityindicator, a node description, or node class information (by operation3233). Alternatively or additionally, module 1150 can perform one ormore of operation 3239 of evaluating a probability of an availability ofa resource or operation 3236 of obtaining an indication of anavailability of a node. Module 1150 can optionally be configured toinclude a signal-bearing medium (such as memory 1159) bearing one ormore instructions (such as instructions 653, e.g.) for identifying alocation of a node (such as node 1181, e.g.) of thenode-speed-change-prediction-dependent signal route (by operation 3234,e.g.). Circuitry 1170 can perform operation 3256 of transmitting to afirst node route information identifying a second node.

Referring now to FIG. 33, there are shown several variants of flow 500of FIG. 5, such as can be performed by network subsystem 700 of FIG. 7.Module 750 can optionally perform operation 530 of receiving wirelessdata via a node-speed-change-prediction-dependent signal route byperforming one or more of receiving operation 3331, identifyingoperation 3335, receiving operation 3337, or receiving operation 3339.Receiving operation 3331 can be performed by receiving at least aportion of the wireless data in a streaming format. Identifyingoperation 3335 can be performed by identifying at least a message sizeindication in the wireless data, which can be used to estimate atransmission time or to characterize a load on a resource. Receivingoperation 3337 can be performed by receiving at least a data recipientindication in the wireless data. Receiving operation 3339 can beperformed by receiving at least a source indication in the wirelessdata. Optionally the recipient indication and/or source indication areincluded in the relayed portion of the wireless data.

Alternatively or additionally module 770 can optionally performoperation 550 of relaying at least a portion of the wireless data byperforming one or more of broadcasting operation 3355, includingoperation 3356, including operation 3357, or including operation 3358.Broadcasting operation 3355 comprises broadcasting at least the portionof the wireless data. Including operation 3356 comprises including atleast a message length value in a first portion of the wireless data.Including operation 3357 comprises including at least a message lengthvalue in a header of the wireless data. Including operation 3358comprises including at least an estimate of a travel time in thewireless data. The travel time can describe a movement of a signal ordata set, or a movement to a physical object or system, for example. Oneor more intermediate nodes can use the estimate in making a routingdecision, such as by module 1150 determining the signal route dependenton a destination-node-movement speed.

Referring now to FIG. 34, there are shown several variants of flow 500of FIG. 5 or 33, such as can be performed by network subsystem 700 ofFIG. 7. Module 750 can optionally perform operation 530 of receivingwireless data via a node-speed-change-prediction-dependent signal routeby performing one or more of operation 3431, operation 3435, operation3437, or operation 3439. Operation 3431 comprises receiving at least anestimate of a destination-node-movement speed in the wireless data.Operation 3435 comprises receiving at least an estimate of atransmission time in the wireless data. Operation 3437 comprisesreceiving at least automotive traffic data in the wireless data.Operation 3439 comprises receiving at least video data in the wirelessdata.

Additionally or alternatively, module 770 can optionally performoperation 550 of relaying at least a portion of the wireless data byperforming one or more of operation 3455, operation 3456, operation3457, or operation 3458. Operation 3455 comprises including at leastpayment-indicative data in the wireless data. Operation 3456 comprisesincluding at least a source position prediction in the wireless data.Part or all of the prediction optionally affects a routing decision or amessage content. Operation 3457 comprises including at least useridentification data in the wireless data. The data can be received froma user who sent the wireless data from a source node, for example.Operation 3458 comprises correcting at least one error in the wirelessdata, for example by using an error correction code or other constraintdescribing at least some of the data received at operation 530.

Referring now to FIG. 35, there are shown several variants of flow 500of FIG. 5, 33, or 34, such as can be performed by network subsystem 800of FIG. 8. Antenna system 839 can optionally perform operation 530 ofreceiving wireless data via a node-speed-change-prediction-dependentsignal route by performing one or more of operation 3531, operation3535, operation 3537, or operation 3539. Operation 3531 comprisesreceiving at least a service provider identifier in the wireless data.The received identifier need not be a company name but can include anetwork identifier, a service mark, or similar code or other name. Flow500 optionally includes using the identifier in some fashion other thanrelaying it, such as by deciding whether to relay or broadcast the dataportion at least partly dependent on the received identifier. Operation3535 comprises receiving a response via a response route that is notidentical to the determined node-speed-change-prediction-dependentsignal route. For example, the response route is optionally generatedafter the relaying operation 550 is complete. Alternatively oradditionally, subsystem 800 can define a circuitous data flow routethrough a destination node, fully specifying the response route to thedestination node. Operation 3537 comprises displaying at least anindication of the wireless data in a mobile node within thenode-speed-change-prediction-dependent signal route. For example, someor all of the received data may be displayed to user 885 via interface836. Operation 3539 comprises displaying at least an indication of thewireless data within a stationary node along thenode-speed-change-prediction-dependent signal route. For example, theindication may include displaying a title or owner or other message ornetwork attribute(s), video or other content data, an indication of adata type or format, a transmission duration or size, or merely a “busy”light or icon.

Additionally or alternatively, communication system 830 can performoperation 550 of relaying at least a portion of the wireless data byperforming one or more of operation 3552, operation 3556, operation3557, or operation 3558. Operation 3552 comprises receiving a predictionof a node speed change. The prediction may relate to a node within thesignal route or to a candidate for addition to a signal route, forexample, or to some other node as may be convenient for regular oroccasional sharing of useful routing information. The node may beredundant at the time of the relaying operation, for example, but becomeimportant later. Operation 3556 comprises including at leastmeteorological data in the wireless data. Operation 3557 comprisesincluding at least medical or meteorological data in the wireless data.(Medical and meteorological data can be difficult to access orcommunicate satisfactorily by conventional techniques, especially fromor at locations inadequately serviced by stationary antennas.).

Module 1150 of FIG. 11 can likewise perform operation 530, optionallyincluding operation 3539 of displaying at least an indication of thewireless data within a stationary node along thenode-speed-change-prediction-dependent signal route. Processor 1153 ofmodule 1150 can optionally be configured to perform this operation, forexample, in an embodiment in which the stationary node includes module1150.

Alternatively or additionally, circuitry 1170 can perform the operation550 of relaying at least a portion of the wireless data, optionallyincluding operation 3558 of establishing a bidirectional channel alongat least a portion of the determinednode-speed-change-prediction-dependent signal route. Transceiver 1174 ofcircuitry 1170 can be configured to perform this operation, for example,by establishing the bidirectional channel (across a free space mediumdirectly) to mobile node 1181.

Referring now to FIG. 36, there are shown several variants of flow 500of FIG. 5, 33, 34, or 35. Network subsystem 700 of FIG. 7 can optionallybe configured to perform one or more of these variants. Module 750 canoptionally perform operation 530 of receiving wireless data via anode-speed-change-prediction-dependent signal route by performing one ormore of operation 3631, operation 3636, operation 3637, or operation3639. Antenna 754 can be configured to perform the operation 3631 ofreceiving a response via a response route substantially identical to thedetermined node-speed-change-prediction-dependent signal route, forexample. Alternatively or additionally, controller 759 can be configuredfor performing the operation 3636 of routing a first portion of thewireless data further along the determinednode-speed-change-prediction-dependent signal route (via circuitry 770,e.g.) before receiving a substantial remainder of the wireless data.Amplifier 751 can be configured to perform the operation 3637 ofconverting at least a portion of the wireless data into a radiofrequency signal. This can be useful in an embodiment in which module750 is not linked to circuitry 770 by any conduit, for example, tofacilitate a short-range wireless transmission to circuitry 770 of someor all of the received data. Alternatively or additionally, controller758 can perform the operation 3639 of routing at least a portion of thewireless data to a passenger vehicle. Controller 758 can do so byidentifying the passenger vehicle with the data to be transmitted to thecircuitry 770, for example.

Circuitry 770 can optionally perform operation 550 of relaying at leasta portion of the wireless data by performing one or more of operation3655, operation 3656, operation 3657, or operation 3658. Circuitry 770can optionally perform operation 3655 of alerting a user within a mobilenode about the received wireless data. For example, controller 778 canoptionally be configured to alert the user. Subsystem 700 can be a toweror other stationary structure or a hand-held device operable to alertthe user.

Alternatively or additionally, controller 778 can also be a vehiclehaving a driver or other occupant as the user within the mobile node.Controller 778 can optionally perform operation 3656 of relaying atleast some state information in the wireless data. Memory 779 canoptionally perform operation 3657 of storing at least a portion of thereceived wireless data. Circuitry 770 can optionally perform operation3658 of routing a response to the wireless data upstream along thesignal route. The response can include an acknowledgment or anasynchronous signal, for example.

Referring now to FIG. 37, there are shown several variants of flow 500of FIG. 5, 33, 34, 35 or 36. Node 140 of FIG. 1 can optionally beconfigured to perform one or more of these variants, for example. Node140 can likewise perform one or more of operation 3731 of routing atleast a portion of the wireless data to a motor-propelled vehicle,operation 3733 of routing at least a portion of the wireless datathrough a tower to a vehicle, or operation 3736 of routing at least aportion of the wireless data to a medical facility. A “motor-propelledvehicle” is not limited to a vehicle currently in transit, but alsoincludes motorized vehicles that are stationary and/or powered off.Alternatively or additionally, node 140 can perform operation 3734 ofrouting at least a portion of the wireless data through a stationarynode and a mobile node. The stationary node and the mobile node can benode 154 and node 156, for example, optionally respectively.

Alternatively or additionally, node 140 can perform one or more ofoperation 3755 of routing a response to the wireless data toward anupstream node of the signal route or operation 3757 of transmitting atleast a portion of the wireless data into an optical fiber. Node 140 canlikewise perform operation 3756 of sending a portion of the wirelessdata along the determined node-speed-change-prediction-dependent signalroute without awaiting an acknowledgment signal. Operation 3756 does notpreclude taking some other action responsive to an acknowledgmentsignal, though, such as sending another portion.

Referring now to FIG. 38, there are shown several variants of flow 500of FIG. 5, 33, 34, 35, 36 or 37. Node 154 of FIG. 1 can optionally beconfigured to perform one or more of these variants. Node 154 canperform one or more of operation 3831 of routing at least a portion ofthe wireless data from a medical device, operation 3833 of receiving atleast state information with the wireless data, operation 3834 ofidentifying an acceptable error level in at least a portion of thewireless data, operation 3835 of detecting a node speed change, oroperation 3839 of correcting at least a portion of the wireless data.Alternatively or additionally, node 154 can perform operation 3836 ofrequesting a prediction of a node speed change. Node 154 can performoperation 3838 of responding to a prediction of a node speed change, forexample after receiving a response or other information that includes aprediction of a node speed change,

Alternatively or additionally, node 156 is configured to perform part orall of flow 500, including performing relaying operation 550 byperforming one or more of operation 3855, operation 3856, operation3857, or operation 3858. Operation 3855 comprises routing at least aportion of the wireless data through a mobile node (which can be node190, e.g.). Operation 3856 comprises routing at least a portion of thewireless data via a satellite (which can be node 190, e.g.). Operation3857 comprises routing at least a portion of the wireless data through anon-motorized device (which can be node 190, e.g.). Operation 3858comprises including at least an indication of a vehicle speed in thewireless data. Optionally the speed describes a measured or estimatedspeed of a vehicle having a wireless communication device such as areceiver.

Referring now to FIG. 39, there are shown several variants of flow 500of FIG. 5, 33, 34, 35, 36, 37, or 38. Node 154 of FIG. 1 can optionallybe configured to perform one or more of these variants that include oneor more of operation 3931, operation 3935, operation 3937, or operation3939. Operation 3931 includes broadcasting a descriptor of anintermediate node to one or more nodes outside thenode-speed-change-prediction-dependent signal route. The broadcastoperation 3931 can optionally be performed by the intermediate node(such as by node 154, e.g.). Alternatively, a node (such as node 154)can broadcast a descriptor of a downstream intermediate node (such asnode 156, e.g.), an upstream intermediate node (such as node 140, e.g.),or a node (such as node 190, e.g.) that is not consecutive with thebroadcasting node. A node that receives the descriptor can be adestination node (such as node 197) not yet within the signal route, forexample, or a candidate or other node that is not yet within the signalroute from the source node(s). Also a receiving node can receive thebroadcast via other nodes within the signal route.

At operation 3935, a system (such as node 154, e.g.) can transmit stateinformation of an intermediate node (such as node 140, node 154, node156, or node 190, e.g.) to a next-upstream-node (such as node 140, e.g.,in an embodiment in which node 140 is consecutive with node 154).Operation 3937 includes indicating a suitability of a mobile node, suchas by transmitting a suitability-indicative scalar to a router. Node 154can also perform operation 3937 by receiving and using a suitabilityindicator of a mobile node. Alternatively or additionally, node 154 canperform operation 3939 of evaluating a suitability of thenode-speed-change-prediction-dependent signal route by performing anarithmetic calculation.

Many of the above-described variants can be performed by a downstreamnode 156 as well. Alternatively or additionally, node 156 can beconfigured to perform one or more of operation 3954 of predicting a nodespeed change, operation 3955 of indicating at least a speed change inthe wireless data, operation 3956 of including at least a speed changeprediction in the wireless data, operation 3957 of identifying at leastan erroneous portion of the wireless data.

Referring now to FIG. 40, there are shown several variants of flow 500of FIG. 5, 33, 34, 35, 36, 37, 38, or 39. Subsystem 700 of FIG. 7 can,in various embodiments, perform any of these flow variants. Anembodiment of subsystem 700 that includes none of the optional featuresof FIG. 7 (i.e., those labeled conventionally by dashed lines) canoptionally perform operation 4031, operation 4035, operation 4037,operation 4040, operation 4055, operation 4056, operation 4057, oroperation 4058. For example, module 750 can perform operation 4031 ofreceiving a suitability indication of a signal route (such as route 182of FIG. 1, e.g.) other than the node-speed-change-prediction-dependentsignal route (such as route 180, e.g.). Module 750 can perform operation4035 of receiving an indication that a node speed will decrease. Module750 can perform operation 4037 receiving a predictive indication of anode stopping. Alternatively or additionally, module 750 can performoperation 4040 of receiving a predictive indication of a node turning.For an embodiment in which subsystem 700 is a land vehicle, thepredictive indication may include a non-linear route or schedule ofnon-colinear stops, for example.

Also circuitry 770 can perform operation 4055 of indicating a positionindex of an upstream node to a downstream node (such as by indicating aposition index of node 154 to node 190 of FIG. 1, e.g.). Circuitry 770can perform operation 4056 of indicating a position of a downstream nodeto an upstream node (such as by indicating a position index of node 154to node 140, e.g.). Circuitry 770 can perform operation 4057 ofindicating a type of a first node to a second node. Alternatively oradditionally, circuitry 770 can perform operation 4058 of indicating asuitability of a stationary node.

Referring now to FIG. 41, there are shown several variants of flow 500of FIG. 5, 33, 34, 35, 36, 37, 38, 39, or 40. Subsystem 700 of FIG. 7can perform optional operation 4131, operation 4132, operation 4135,operation 4137, operation 4156, operation 4157, operation 4158, oroperation 4159. Any of these optional operations 4131-4159 can beperformed substantially in concert with any of the other variants offlow 500 described above.

For example, module 750 can perform operation 4131 of receiving anindication of a node turning. Module 750 can perform operation 4132 ofreceiving a predictive indication of a node powering off. This can beimplemented in concert with circuitry 772 for implementing atime-dependent traffic model, for example, to generate or otherwiseobtain a prediction that a vehicle will power off imminently. (Such aprediction may arise by detecting a vehicle entering a residential lotat 11 p.m., for example.) Module 750 can likewise perform operation 4135of receiving a predictive indication of a node going offline.Alternatively or additionally, module 750 can perform operation 4137 ofreceiving a predictive indication of a node encountering a local servicelevel change. Such an indication may depend on one or more speed limits,for example, especially if expressed as an amount of time.

Also circuitry 770 can perform operation 4156 of relaying a suitabilityindicator to the node-speed-change-prediction-dependent signal route.Circuitry 770 can perform operation 4157 of identifying one or moredownstream node candidates to a downstream node. Circuitry 770 canperform operation 4158 of beginning an operation before finishing thereceiving wireless data via a node-speed-change-prediction-dependentsignal route. Alternatively or additionally, circuitry 770 can performoperation 4159 of receiving additional wireless data via thenode-speed-change-prediction-dependent signal route before finishingrelaying the portion of the received wireless data.

Referring now to FIG. 42, there are shown several additional variants offlow 400 of FIG. 4 or 41. For example, subsystem 1100 of FIG. 11 canoptionally perform operation 4232 of including at least an estimate ofan arrival time in the data or operation 4234 of routing at least aportion of the data through a passenger vehicle. The including operation4232 can optionally be complete before circuitry 1170 begins routingoperation 450. Operation 450 can optionally include operation 4251 oftransmitting the data, operation 4254 of arranging the data into one ormore packets and operation 4255 of transmitting the data via a freespace medium, or operation 4257 of performing a retry operation.Operation 4251 can be performed by controller 1171, for example, and canoptionally include operation 4252 of transmitting state information withthe data or operation 4253 of transmitting the data via a free spacemedium. Operation 4254 or operation 4257 can optionally be performed bycontroller 1171, alternatively or additionally, as can operation 4258 ofperforming a retry operation using a compound route.

Referring now to FIG. 43, there are shown several additional variants offlow 400 of FIG. 4, 41, or 42. For example, module 1150 of FIG. 11 canoptionally perform operation 430 of obtaining a node identifierdependent on at least a position index and a loading indicator of amobile node by performing one or more of operation 4332, 4334, oroperation 4336. Processor 1153 of module 1150 can optionally perform oneor more of operation 4332 of updating state information in the data,operation 4334 of indicating a position of an intermediate node to anext-upstream-node, or operation 4336 of broadcasting the loadindicator, for example.

Module 1170 can optionally perform one or more of the operation 4355 ofincluding at least a data priority indication in the data, the operation4357 of including at least a data ownership indication in the data, orthe operation 4358 of including at least a destination indication in thedata. Medium 1172 can optionally perform the operation 4351 ofdisplaying at least an indication of the data at the mobile node.Alternatively or additionally, transmitter 1173 can perform theoperation 4354 of streaming at least a portion of the data.

Referring now to FIG. 44, there are shown several additional variants offlow 400 of FIG. 4, 42, or 43. For example, node 140 of FIG. 1 canoptionally perform flow 400 such as by substantially any of the abovevariants of flow 400. Alternatively or additionally, node 140 canperform one or more of operation 4431 of indicating a suitability of asignal route (optionally including operation 4432 of indicating asuitability of an intermediate node), operation 4433 of performing anoperation while routing data through the mobile node responsive to thenode identifier, or operation 4436 of receiving a latitude and alongitude of the mobile node.

Node 133 of FIG. 1 can likewise perform flow 400 such as bysubstantially any of the above variants of flow 400. Alternatively oradditionally, node 133 can perform one or more of operation 4451 ofincluding at least a destination position index in the data, operation4452 of encrypting at least a portion of the data, operation 4454 ofreserving a route, operation 4455 of displaying at least a portion ofthe data via an element of a mobile node, or operation 4456 of awaitingan acknowledgment signal before sending a portion of the data. Forexample, node 133 can receive the acknowledgment signal from node 140.

Node 190 of FIG. 1 can likewise perform flow 400 such as bysubstantially any of the above variants of flow 400. Alternatively oradditionally, node 190 can perform one or more of operation 4458 ofconverting at least a portion of the data into an optical signal oroperation 4457 of multiplexing at least a portion of the data. Theformer will be expedient if, for example, linkage 195 includes a longhaul fiberoptic conduit.

Referring again to FIG. 12, in an alternate embodiment, computer programproduct 1220 can be configured to include a recordable medium 1246 asthe signal-bearing medium 650 of FIG. 6. More particularly therecordable medium 1246 can contain instructions 654 including one ormore instructions for performing routing operation 450. The one or moreincluded instructions can optionally comprise: one ore more instructionsfor performing one or more operations of operations 4251 through 4458.One embodiment, for example, is a computer program product (product1220, e.g.) comprising a signal-bearing medium (medium 650, e.g.)bearing at least one of: one or more instructions for obtaining a nodeidentifier dependent on at least a position index and a loadingindicator of a mobile node; and one or more instructions for streamingat least a portion of the data and for routing data through the mobilenode responsive to the node identifier (by operation 450 with operation4354, e.g.).

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from this subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of this subject matter describedherein. Furthermore, it is to be understood that the invention is solelydefined by the appended claims. It will be understood by those withinthe art that, in general, terms used herein, and especially in theappended claims (e.g., bodies of the appended claims) are generallyintended as “open” terms (e.g., the term “including” should beinterpreted as “including but not limited to,” the term “having” shouldbe interpreted as “having at least,” the term “includes” should beinterpreted as “includes but is not limited to,” etc.). It will befurther understood by those within the art that if a specific number ofan introduced claim recitation is intended, such an intent will beexplicitly recited in the claim, and in the absence of such recitationno such intent is present. For example, as an aid to understanding, thefollowing appended claims may contain usage of the introductory phrases“at least one” and “one or more” to introduce claim recitations.However, the use of such phrases should not be construed to imply thatthe introduction of a claim recitation by the indefinite articles “a” or“an” limits any particular claim containing such introduced claimrecitation to inventions containing only one such recitation, even whenthe same claim includes the introductory phrases “one or more” or “atleast one” and indefinite articles such as “a” or “an” (e.g., “a” and/or“an” should typically be interpreted to mean “at least one” or “one ormore”); the same holds true for the use of definite articles used tointroduce claim recitations. In addition, even if a specific number ofan introduced claim recitation is explicitly recited, those skilled inthe art will recognize that such recitation should typically beinterpreted to mean at least the recited number (e.g., the barerecitation of “two recitations,” without other modifiers, typicallymeans at least two recitations, or two or more recitations).Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that any disjunctive word and/orphrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.” Moreover, “can”and “optionally” and other permissive terms are used herein fordescribing optional features of various embodiments. These termslikewise describe selectable or configurable features generally, unlessthe context dictates otherwise.

The herein described aspects depict different components containedwithin, or connected with, different other components. It is to beunderstood that such depicted architectures are merely exemplary, andthat in fact many other architectures can be implemented which achievethe same functionality. In a conceptual sense, any arrangement ofcomponents to achieve the same functionality is effectively “associated”such that the desired functionality is achieved. Hence, any twocomponents herein combined to achieve a particular functionality can beseen as “associated with” each other such that the desired functionalityis achieved, irrespective of architectures or intermedial components.Likewise, any two components so associated can also be viewed as being“operably connected,” or “operably coupled,” to each other to achievethe desired functionality. Any two components capable of being soassociated can also be viewed as being “operably couplable” to eachother to achieve the desired functionality. Specific examples ofoperably couplable include but are not limited to physically mateableand/or physically interacting components and/or wirelessly interactableand/or wirelessly interacting components and/or logically interactableand/or logically interacting components.

While certain features of the described implementations have beenillustrated as disclosed herein, many modifications, substitutions,changes and equivalents will now occur to those skilled in the art. Itis, therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the true spiritof the embodiments of the invention.

1. A network subsystem comprising: (a) means for receiving wireless datavia a node-speed-change-prediction-dependent signal route, the means forreceiving the wireless data including at least (1) means for receivingat least video data, a predictive indication of an intermediate nodeturning, and an estimate of a transmission time in the wireless data;(2) means for indicating a suitability of the intermediate node; (3)means for broadcasting a descriptor of the intermediate node to one ormore nodes outside the node-speed-change-prediction-dependent signalroute; and (4) means for displaying at least an indication of thewireless data within a stationary node along thenode-speed-change-prediction-dependent signal route; and (b) means forrelaying at least a portion of the wireless data.
 2. A network subsystemcomprising: (a) means for receiving wireless data via anode-speed-change-prediction-dependent signal route; and (b) means forrelaying at least a portion of the wireless data, the means for relayingincluding at least (1) means for indicating a suitability of astationary node and a type of the stationary node to a satellite; (2)means for identifying one or more other downstream node candidates tothe satellite; routing at least a portion of the wireless data via thesatellite; (3) means for including at least user identification data ora source position prediction in the portion of the wireless data; and(4) means for sending at least some meteorological or medical data inthe wireless data along the signal route without awaiting anacknowledgment signal.
 3. A network subsystem comprising: (a) means forreceiving wireless data via a node-speed-change-prediction-dependentsignal route; and (b) means for relaying at least a portion of thewireless data, the means for relaying including at least (1) means forincluding at least meteorological or medical data in the wireless data;(2) means for sending one or more of payment-indicative data or useridentification data of the wireless data along thenode-speed-change-prediction-dependent signal route without awaiting anacknowledgment signal; and (3) means for identifying one or moredownstream node candidates to a downstream node.
 4. The networksubsystem of claim 1, wherein the means for receiving wireless data viaa node-speed-change-prediction-dependent signal route comprises: meansfor receiving at least an estimate of a destination-node-movement speedin the wireless data.
 5. The network subsystem of claim 1, wherein themeans for receiving wireless data via anode-speed-change-prediction-dependent signal route comprises: means forreceiving at least an estimate of a transmission time in the wirelessdata.
 6. The network subsystem of claim 1, wherein the means forreceiving wireless data via a node-speed-change-prediction-dependentsignal route comprises: means for receiving at least video data in thewireless data.
 7. The network subsystem of claim 1, wherein the meansfor receiving wireless data via a node-speed-change-prediction-dependentsignal route comprises: means for receiving at least a service provideridentifier in the wireless data.
 8. The network subsystem of claim 1,wherein the means for receiving wireless data via anode-speed-change-prediction-dependent signal route comprises: means forindicating the wireless data in a mobile node within thenode-speed-change-prediction-dependent signal route.
 9. The networksubsystem of claim 1, wherein the means for receiving wireless data viaa node-speed-change-prediction-dependent signal route comprises: meansfor receiving a response via a response route substantially identical tothe node-speed-change-prediction-dependent signal route.
 10. The networksubsystem of claim 1, wherein the means for receiving wireless data viaa node-speed-change-prediction-dependent signal route comprises: meansfor routing at least the portion of the wireless data through thestationary node.
 11. The network subsystem of claim 1, wherein the meansfor receiving wireless data via a node-speed-change-prediction-dependentsignal route comprises: means for correcting at least the portion of thewireless data.
 12. The network subsystem of claim 1, wherein the meansfor receiving wireless data via a node-speed-change-prediction-dependentsignal route comprises: means for indicating a suitability of theintermediate node.
 13. The network subsystem of claim 1, wherein themeans for receiving wireless data via anode-speed-change-prediction-dependent signal route comprises: means forevaluating a suitability of the node-speed-change-prediction-dependentsignal route by performing an arithmetic calculation.
 14. The networksubsystem of claim 1 wherein the means for receiving wireless data via anode-speed-change-prediction-dependent signal route comprises: means forreceiving a predictive indication of the intermediate node goingoffline.
 15. The network subsystem of claim 1, wherein the means forreceiving wireless data via a node-speed-change-prediction-dependentsignal route comprises: means for receiving a predictive indication ofthe intermediate node encountering a local service level change.
 16. Thenetwork subsystem of claim 1, wherein the means for relaying at least aportion of the wireless data comprises: means for including at least amessage length value in a header of the wireless data.
 17. The networksubsystem of claim 1, wherein the means for relaying at least a portionof the wireless data comprises: means for including at least an estimateof a travel time in the wireless data.
 18. The network subsystem ofclaim 1, wherein the means for relaying at least a portion of thewireless data comprises: means for including at least payment-indicativedata in the wireless data.
 19. The network subsystem of claim 1, whereinthe means for relaying at least a portion of the wireless datacomprises: means for including at least a source position prediction inthe wireless data.
 20. The network subsystem of claim 1, wherein themeans for relaying at least a portion of the wireless data comprises:means for including at least user identification data in the wirelessdata.
 21. The network subsystem of claim 1, wherein the means forrelaying at least a portion of the wireless data comprises: means forincluding at least some photographic image data in the wireless data.22. The network subsystem of claim 1, wherein the means for relaying atleast a portion of the wireless data comprises: means for including atleast meteorological data in the wireless data.
 23. The networksubsystem of claim 1, wherein the means for relaying at least a portionof the wireless data comprises: means for including at least medicaldata in the wireless data.
 24. The network subsystem of claim 1, whereinthe means for relaying at least a portion of the wireless datacomprises: means for establishing a bidirectional channel along at leasta portion of the node-speed-change-prediction-dependent signal route.25. The network subsystem of claim 1, wherein the means for relaying atleast a portion of the wireless data comprises: means for sending theportion of the wireless data along thenode-speed-change-prediction-dependent signal route without awaiting anacknowledgment signal.
 26. The network subsystem of claim 1, wherein themeans for relaying at least a portion of the wireless data comprises:means for transmitting at least the portion of the wireless data into anoptical fiber.
 27. The network subsystem of claim 1, wherein the meansfor relaying at least a portion of the wireless data comprises: meansfor routing at least the portion of the wireless data via a satellite.28. The network subsystem of claim 1, wherein the means for relaying atleast a portion of the wireless data comprises: means for including atleast an indication of a vehicle speed in the wireless data.
 29. Thenetwork subsystem of claim 1, wherein the means for relaying at least aportion of the wireless data comprises: means for indicating a type ofthe stationary node.
 30. The network subsystem of claim 1, wherein themeans for relaying at least a portion of the wireless data comprises:means for indicating a suitability of another stationary node.
 31. Thenetwork subsystem of claim 1, wherein the means for relaying at least aportion of the wireless data comprises: means for identifying one ormore downstream node candidates to a downstream node.
 32. The networksubsystem of claim 1, wherein the means for receiving wireless data viaa node-speed-change-prediction-dependent signal route comprises: anantenna operable to receive the wireless data; and a driver configuredto adapt a directionality of the antenna.
 33. The network subsystem ofclaim 1, wherein the means for receiving wireless data via anode-speed-change-prediction-dependent signal route comprises: a userinterface operable to display at least the portion of the wireless data.34. The network subsystem of claim 1, wherein the means for relaying atleast a portion of the wireless data comprises: circuitry forimplementing a location-dependent speed model.
 35. The network subsystemof claim 1, wherein the means for relaying at least a portion of thewireless data comprises: circuitry for implementing a vehicle-dependentspeed model.
 36. The network subsystem of claim 1, further comprising: apassenger vehicle containing the means for receiving the wireless datavia the node-speed-change-prediction-dependent signal route.
 37. Thenetwork subsystem of claim 1, wherein the means for relaying at leastthe portion of the wireless data comprises: means for including anestimate of a travel time, payment-indicative data, a source positionprediction, and user identification data in the wireless data; means forincluding at least an indication of a vehicle speed in the wirelessdata; means for including at least meteorological or medical data in thewireless data; means for sending a message length value in a header ofthe wireless data along the node-speed-change-prediction-dependentsignal route without awaiting an acknowledgment signal; means forestablishing a bidirectional channel along at least a portion of thenode-speed-change-prediction-dependent signal route; means forindicating a type of the intermediate node to the stationary node; meansfor identifying one or more downstream node candidates to a downstreamnode; and means for routing a response to the wireless data upstreamalong the signal route.
 38. The network subsystem of claim 2, whereinthe means for receiving wireless data via anode-speed-change-prediction-dependent signal route comprises: means fordisplaying at least an indication of the wireless data in a passengervehicle within the node-speed-change-prediction-dependent signal route;means for correcting at least a portion of the wireless data; and meansfor receiving at least a service provider identifier, a predictiveindication of another node going offline, and an estimate of adestination-node-movement speed in the wireless data.